Main Overview

                                    see System Quirks

 

 

The Main Overview screen provides the launch point for general information about the health of the System.

 

The top left side of the screen contains the System name, System serial number and operating system version.  The next two fields provide the state of TMF and the current transactions per second.  The TMF State displays the percent utilization of the audit trail (largest value is displayed if TMF is configured with auxiliary audit trails).

 

The fields in the lower left handle corner Busy %, CPU que, Pressure and Disk i/o display the Overall CPU busy, average CPU queue depth, memory pressure (a value from 0 to 7 where 7 is the highest) and physical disk I/Os per second respectively.  Additionally, these fields are used to relate special information as described below.   

 

If MEASURE is not started, MEAS is reported in each affected processor.  Use MEASCOM to start the MEASURE subsystem (for the system or a particular processor):

 

 

 

If a MOMI CPU collector process does not report in a timely manner, typically after 30 seconds, STOP is reported.  MOMI then issues a Guardian stop on the collector process and the process is automatically restarted by MOMI (the automatic restart occurs approximately 1 minute after the STOP is displayed).  Technically, the processor is marked as HUNG but this is usually not visible if the CPU collector process stops as directed:

 

                                      

 

 

In the event a CPU fails, the following is displayed for the affected CPU (the MOMI CPU collector automatically restarts approximately 1 minute after the CPU is reloaded):

 

 

 

TMF State reports the general status of TMF (Started, Stopped, etc...) along with overflow and other error indicators.  The percentage full (i.e. in use) of the largest of the Master (MAT) or Auxiliary (AUXnn) audit trails is also reported in parentheses for most states.  Generally speaking, the "worst" state or condition is selected for display.

 

Below are some sample TMF States:

 

 Master audit trail at 11% full

 

 

 Auxiliary audit trail 1 at 33% full

 

Auxiliary audit trail 1 at 77% full

 

Auxiliary audit trail 1 cannot rollover (out of space and no overflow available)

 

Auxiliary audit trail 1 using overflow

 

Begin transactions disabled within TMF

 

 

The right side of the screen shows the busiest or top processes on the entire System.  The fields listed are the CPU + PIN , process name (blank if unnamed), current priority, PFR fields, object file name and percent busy.

 

The Busy% field is the percentage of total CPU busy for the process during the last monitored interval (by default MOMI scans the CPUs every 10 seconds).

 

The Pri field is the current process priority field.  The surrounding box is yellow if the operating system has reduced the process priority and the process is a disk.  A red color is used for any other process with a reduced priority.  Disk processes will assume the priority of the requesting process while waiting for executing time.  It is normal to see a disk process running at different priorities.  User processes have their priority lowered by the System if they are determined to be CPU bound (i.e. taking a great deal of CPU resources).

 

The PFR fields indicate with single letter descriptors if the process is P - Privileged , F - page Faulting or R - on the Ready list.  A process is Privileged if it has been granted authority to run without security limitations (many System processes are Privileged).  A process needing memory space is page Faulting during the time it takes to free or swap needed memory pages.  A process is on the Ready list when it is waiting for CPU execution.  Additionally, a process can be on the Ready list while waiting on a page Fault.

 

Placing the mouse over the CPU,PIN field will cause a pop-up window to appear that presents additional process information.  Below is a sample image:

 

 

 

A right click on the CPU,PIN or Process field will bring up a menu allowing the User to select a variety of jumps or actions using the selected process (the actions available vary depending on the process):